We discovered some more logs that we forgot to include in our last issue! Also, his lameness struck again, this time as "RobertM" claiming to be 25 years of age and about to earn his PhD in Adolescant Psychology! Quite a jump from the high school junior that he was posing as just a week earlier. Unfortunately, these logs were filled with too much lameness to include in this DOCMaker issue, you may browse them on our website though (what a relief, eh?). Check 'em out:
He's also been posing as "Trixxer" -- claiming to be PPC604e's cousin, but really PPC604e in lame disguise. Remember, always look for that pacbell.com domain!
• How to play Command & Conquer •
Many people are still confused about how to play Command & Conquer, well
this faq will solve all your problems. I have seen many that say this
will allow you to play all of NOD and only the first of GDI, well follow
these instructions and you can play all levels of both NOD and GDI.
1. Run the c&c installer, after you have installed it delete anf files
that are related to the install. All of the install files have the word install in them.
2. Next look in the name the 2 folders NOD and GDI.
3. After that look in one of the foldesr, it *should* be the NOD folder.
One will have only 1 file thats called GENERAL.MIX and the other
will have GENERAL.MIX and like 10 or 15 other files. Copy all of
the files except GENERAL.MIX into the folder with only GENERAL.MIX.
4. After this, run your proggie that will mount the Folders as images.
Mount both the folders, make sure they are named GDI and NOD.
5. Once the images are mounted, run c&c, you will be able to play either
GDI or NOD and you can play the full game on both.
- Plugs
• Flooding Part II •
Welcome to part two of the flooding series in EMC. This will be a very elaborate article about all aspects of flooding, from protecting yourself, how to flood, and which tools to use. I encourage you to read this *entire* article so that you fully understand flooding and what it does. So, without further ado EMC presents to you:
 
This FAQ assumes you have general (preferably, above-average) knowledge of IRC. This FAQ also covers flooding using Macintosh IRC clients, not shell accounts. FloodFAQ 2.0 will cover strategies and methods of flooding using shell accounts. (2.0 will probably be featured in or before EMC Volume #15.)
What Does Flooding Do?
There are several types of floods that can be used on IRC, all have the same objective: To get you flooded off. Basically, if you are being flooded, it is to get you off of IRC. For what reason? Well, it could be a number of things: you might have pissed someone off, you might have taken someone's nick, you might be lame, etc. etc. In any event, the flooder's goal is to get you off of IRC.
How Do You Know If You're Being Flooded?
That's pretty simple, (in Ircle) you'll see a number of CTCP requests scrolling in your console or current channel window:
*** Replied (private) CTCP FINGER from Freakman
*** Replied (private) CTCP USERINFO from Freakman
*** Replied (private) CTCP PING 850837268 from Freakman
*** Replied (private) CTCP USERPROFILE from Freakman
ICMP floods are something a little different. These (sometimes) aren't even done on IRC, but from computer to computer. Programs like OTTool 1.0b4 have an option to ping an ip, and if the person who is icmp flooding you is smart enough, they'll have it configured just right so that it sends thousands of pings to your computer. You'll know when you're being flooded this way because your modem lights will be flashing like mad.
How Do You Prevent Yourself From Being Flooded?
Luckily, there are a number of things to do. When you are being flooded with CTCP requests while on IRC and using Ircle, you can take advantage of the "C.Toggle" button.
If you start seeing an excessive number of ctcp requests on your screen, TURN OFF CTCP REQUESTS. By turning off CTCP requests, you no longer will accept any CTCP requests, thus preventing you from being flooded.
So, how do you toggle CTCP requests on and off? This is configured in Ircle within the preferences window under your Buttons menu. "C.Toggle" is the button name, it is a *very* wise choice to have this button in your button list. Since it is a toggle, CTCP requests can be turned on and off with the click of the mouse.
The only way to avoid ICMP floods for the time being is to log off and log back on to your ISP (assuming you have a dynamic IP). However, if the remote flooder knows what they're doing, they'll finger your account and find out whether or not you're online, and if you are, they have your current IP so they can start flooding again. This doesn't happen too often, but when it does, it can be one of the most annoying things. Because of the constant stream of pings being sent from and replied to, your entire session will be lagged to high hell. If you are still being flooded after you sign off and sign back on with a different IP, it's a good idea to call it quits for the day (or weekend, or week, or month, depending how dedicated the flooder is).
The Breakdown of What Each Flood Does and Which Are Most Effective
1. /ctcp nick finger, /ctcp nick userinfo, /ctcp nick userprofile, and /ctcp nick version will most likely be used together in a flood. What makes these effective is that when each CTCP request is received, your computer retrieves the data to reply to that CTCP request. While your computer is retrieving that data, more of these CTCP requests are made. The more that are made, the faster you are flooded of IRC. Your signoff message will be "Excess Flood" and you will simply be reconnected to your current irc server. While disconnected, the flooder has enough time to change his/her nick the nick you had before being flooded off.
These ctcp floods are most effective when using clones. Clones are merely multiple irc sessions in Ircle. 3-5 clones is more than enough to flood a user without flood protection off of IRC. BUT, if the person being flooded turns off CTCP requests, your flooding is worthless. The best time to flood someone is to catch them off guard, that way they cannot manually toggle CTCP requests on and off. However, somebody who has their shit together will have a script that detects CTCP floods, and will protect them even when they are not alert and at their computer. These types of floods are very effective against mIRC users (without flood protection), somewhat effective against Irlce users (when CTCP requests are active), and ShadowBots (when CTCP requests are active).
2. ICMP floods are most effective when flooding from a high speed connection to a connection that is slower. T1 floods to a 28.8 dialup will get anyone to ping timeout in no time. 28.8 dialup -> 28.8 dialup is practically useless, unless you have a group of people flooding to one dialup from their dialups. So, you get the idea. The more people flooding one ip from whatever kindo f connection they have, the faster that person is flooded off. Their signoff message will be "Ping Timeout." ICMP floods (if done right) will result in a carrier drop of a dialup connection (if on a dialup connetion).
3. Flash flooding freezes up some unix shells. The best thing to do is to do it multiple times, but since these types of floods rarely work (with what's available for Flash Flood apps) so I won't go into detail.
What Tools Do I Need In Order To Flood?
For DCC bombs, CTCP floods, Beep Floods, or Nick Floods, you'll need Death v2.1 by The ScriptLords (used in conjunction with Ircle).
For ICMP Floods, you'll need a fast connection or a multiple dialups (help of friends takes care of this) and the program called OTTool 1.0b4. The url for OTTool is: http://www.neon.com
Friends are *always* a plus to have when flooding other people. The more people you have flooding one person, the faster that person is flooded off of IRC. It is a very wise choice to know a few people that know how to flood and will help you out with flooding when you ask.
I Have The Tools, How Do I Flood?
Using Death 2.1
You must be in Ircle 2.6b7 in order to use Death 2.1 properly. Place Death 2.1 in your active scripting folder for Ircle, otherwise it will not work efficiently. Now you need 3-5
clones online as well. It is a good
idea to establish a private channel 
for yourself and your clones so
that you know that they're all there,
connected, and whatever else. It's
probably not a good idea to flood
from the nick that you use on a
regular basis, so either sign off
temporarily from that nick, or
change your nick.
Launch Death 2.1, select a flood
option from the menubar. Type in
your target nick, enter the number
of clones you have set up, and let
it fly. You'll see the windows in
Ircle change and you'll see the text
being sent to the nick being
flooded. You'll know that the nick has signed off because you'll
get messages saying: *** SomeNick: No such nick/channel
At this point, it's up to you on what you can do. If you were flooding that person to get your nick back, then reclaim your nick! If you were flooding that person to get them out of the channel, cool, your mission is accomplished.
(Plugs is working on yet ANOTHER script, so either him or I will cover how to use its features in the next EMC.)
Using OTTool 1.0b4
Launch OTTool 1.0b4. You need to have the victim's ip before you can icmp flood, so do a /whois nick on the person. You'll see this information:
/whois mama
*** mama is 3maht@U182.N79.QueensU.CA (Mary Ann Turcke)
*** mama is on channels @#tk
*** mama is on IRC via server irc.magic.mb.ca ([ra.magic.mb.ca] Canadian Client & Hub Server)
Look at the hostmask: U182.N79.QueensU.CA Copy and paste that into the field in OTTool. Click on the "DNS" button to resolve the DNS. Now, click on the "Ping" button, configure it like this:
 
Sending 35,000 packets with 0 second interpacket delay waiting no more than 0 seconds for a replay will get pings being sent to the victim in no time. Watch your modem lights go beserk!
When configured, click on "Start" and watch the flooding begin. You'll know your target has been Ping Timed Out because the "Received" field number will not change for quite a while. At this point, take their nick, or do whatever, you've flooded them off!
Flooding Tactics
Here's a few tips and hints when flooding:
When creating clones, it is a good idea *not* to have more than one clone on a server. Even though servers generally allow up to 8 clones before you get K-Lined, IRCops get suspicious when multiple sessions from the same hostmask sign on their server. Your best bet is to have each clone on a different server, it lessens your chance of being K-Lined. Don't be stupid and flood from the server that you consider your "main" server, then you have to rely on other EFNet servers that may be more prone to splits, etc.
Generally, if you're going to take over a channel, you and whoever is helping you should outnumber the ops in the channel. Of course, it is *very* much possible to take over a channel where the ops outnumber you, but it just makes it easier when you've got more people on your side helping out.
ICMP flooding should be used in conjuction with CTCP floods, nick floods, DCC bombs, and whatever else. The reason being that you don't want to constantly send floods from clones on IRC because they'll sign off with Excess Flood (temporarily) and that takes away from the effectiveness of your clones. A good tactic is to send out a couple CTCP floods (from Death 2.1) and then immediately ICMP flood afterwards. These gives your clones some leway between floods, and takes away from the "Excess Flood" signoffs. As long as you're constantly sending packets to your victim, they'll become more and more lagged.
How Do I Know They Are Using Flood Protection and How Do I Defeat It?
You'll know if they have any sort of flood protection on because you won't get any CTCP replies. Sometimes, (if their script is stupid enough) their script will /notice you with a message saying "Excessive CTCP requests deteced from you, you will be ignored for 30 seconds." Giving away the amount of time being ignorde is useless, as you can have other friends flood, and you easily continue after your 30 seconds are up. It's a rather simple strategy.
There's really no way to defeat flood protection, if the person has a good flood protection script running, then you're out of luck with floods on IRC. That's when you use OTTool for ICMP floods. If the victim has a fast connection, you had better have one yourself or have a few friends that'll help out with the ICMP floods, because one dial-up isn't very effective at all.
Nobody Has Ops in the Channel, Now What Should I Do?
Either 1. Find a server that split, get on that server and join the channel you're taking over in hopes that the server will op you when it recovers from the split. Or 2. Flood the rest of the people out of the channel.
Option #1 would be the easiest, but it is difficult to find servers that split, it's basically luck to have a server split right when you get all ops out of the channel--it never seems to work out for your convenience...
Option #2 is very much doable. However, when there are tons of people in the channel, it makes it time consuming to flood everyone out of the channel. But that's what friends are for! At this point, nick flood. It'll get a lot of the people out of the channel, quickly. They'll drop like flies because of Excess Flood. But there are always the few who don't leave the channel for one reason or another. What to do? Flood 'em off. When you've got everyone out of the channel, get your friends to leave the channel and rejoin so you can get ops. Now it's up to you on what to do.
Writing Your Own Flood Scripts
If you have any desire to create your own flood scripts, keep this information in mind:
Most servers start flood protection at 512 bytes in a few seconds, so the trick is to try to force the other person to send lots of bytes with as few as possible bytes sent by you. Therefore, VERSION, GESTALT, and FINGER are a nice floods because for every few bytes you send, they send back a whole line (ore more).
Keeping it at less than 20 or 30 CTCP's from yourself should keep you from being disconnected yourself (Excess Flood). You will probably have to put some delays between each CTCP request, because if you run a script that sends out 10 CTCP versions all without delays, you'll most likely sign off for Excess Flood.
Conclusion
Be smart when flooding, it's very traceable on IRC, and your plans could easily backfire if you flood the wrong person. Don't ICMP flood a shell account because you're really just flooding the ISP itself, and that isn't in the least bit cool.
